|
|
| Author |
Thread Statistics | Show CCP posts - 19 post(s) |
|
CCP Habakuk
C C P
C C P Alliance
151
   |
Posted - 2012.01.09 00:14:00 -
[1] - Quote
Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.
Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers. It might be a good idea to check your hardware or try to disable over-clocking of CPU or GPU.
I suggest to relog your client before risky jumps as workaround till we manage to deploy a fix for this issue. I know that this is annoying and not always possible, but it will reset the clock and so avoid the delay at jumping (but the delay will start accumulating again).
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
154
|
Posted - 2012.01.13 18:37:00 -
[2] - Quote
Hello again!
Our test-server Singularity was updated today with a (potential) fix for this issue. We had to change a bit more than expected, but we are hopeful that the new solution is more stable than before.
I had a short test of this in Singularity, but it would be awesome if you guys (who have this issue on TQ) could try it out! If you already used the test-server at some point or you always wanted to try it: Now is the time for it!
Details: The client is now re-synchronizing with the server every 10 minutes (the time interval might be changed later).
If you are trying this on Singularity, then please take special care of your UI in space after you were logged in for about 10 minutes. Try to jump and dock. It would be great if you are running logserver.exe to get logs for the case that anything breaks - more info at http://wiki.eveonline.com/en/wiki/Logserver. Please send a bugreport if you find any issues (add my name to the title of it) and please also reply in this thread - I will continue to monitor it. It might be possible that 10 minutes is still too long for you guys (if your clock is drifting too fast) and you still have some load lag: please reply in this thread if this is the case.
More information about Singularity can be found here: http://wiki.eveonline.com/en/wiki/Singularity
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
154
|
Posted - 2012.01.15 22:01:00 -
[3] - Quote
Glorious CEO: Thank you a lot for testing it on Singularity!
DurrHurrDurr: How much is a noticeable difference for you? It might be useful, if you could save a logserver log of being ingame for at least 30 minutes while doing stuff and adding this to a bugreport (with the subject including my name).
For the release of this fix: As the fix is a bit more complicated it is not possible to "hotfix" it - it is currently scheduled to be included in the next client patch for Crucible 1.1.
Caroline Grace: These symptoms look a lot like problems with the clock sync - but it might be that your clock is sometimes a bit too fast and sometimes a bit too slow, which would explain the different issues.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
154
|
Posted - 2012.01.15 22:37:00 -
[4] - Quote
DurrHurrDurr wrote:
After 4-8 minutes of being actively in space (ie. shooting a POS, travelling, etc) I notice a difference of about 20-25 seconds between my system clock and the game clock. This gets exaggerated the more I travel and hang around in space. However, the difference doesn't seem to really exceed ~120 seconds.
How do I set up my client to log?
This is some serious clock drift, which you are experiencing there - I'm not sure if we will ever be able to compensate this fully, but it should be at least better with this fix. The instructions for logserver can be found at http://wiki.eveonline.com/en/wiki/Logserver.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
154
|
Posted - 2012.01.15 23:19:00 -
[5] - Quote
DurrHurrDurr wrote:
This issue didn't exist at all before the release of Crucible. Do the devs have any idea what's created the drift?
As far as I know (as lowly QA dude): Before Crucible there was a clock sync at jumping (which was broken with Crucible), but if you stayed within one system you should have drifted like it is now on TQ.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
154
|
Posted - 2012.01.20 16:24:00 -
[6] - Quote
Firebolt145 wrote:CCP could you please give us an eta for Crucible 1.1? It would be much appreciated.
It is planned for Tuesday, the 24th January, as announced in this news message and this DevBlog.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
181
|
Posted - 2012.02.21 00:50:00 -
[7] - Quote
Molic Blackbird, Archinquisitor and Faffywaffy: Could you please write bugreports with logs from logserver.exe, so that I can have a look and check if it is the same old problem (which should be mostly fixed) or if anything new is going on with Crucible 1.2? Please add my name to the title or description, so that I can find the reports more easily.
For all others, who are still experiencing issues: Please also write bugreports about it with included log-files, we will keep trying to find better solutions - maybe there is something in the logs, which help us to pinpoint the remaining issues.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
184
|
Posted - 2012.02.22 16:53:00 -
[8] - Quote
Archinquisitor, Molic Blackbird: Thank you for your bugreports! Your problems are indeed caused by clock drift problems - the drift is too high for our current re-sync system. We had a discussion about this and we will try to solve this with an additional re-sync, which is able to handle high drifts. The release date for this is not decided yet - we will update this thread as soon as it is decided.
You can check for how much your client is drifting in comparison to our server by running logserver.exe and searching the logs. Every 10 minutes following message will be logged, which states the current difference to the server:
*** Soft Clock Sync adjusting by
Btw: We could not find anything, which would explain this to be worse with Crucible 1.2 or which would explain it to be worse in fleets, except that the computer *might* be a bit slower, if it is running at full load (for example during fleet-fights). Please reply here and send bugreports, if you have any additional info.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
184
|
Posted - 2012.02.23 12:21:00 -
[9] - Quote
ISquishWorms wrote:CCP Habakuk wrote:Btw: We could not find anything, which would explain this to be worse with Crucible 1.2 or which would explain it to be worse in fleets, except that the computer *might* be a bit slower, if it is running at full load (for example during fleet-fights). Please reply here and send bugreports, if you have any additional info. I am having this issue as well, while you may not be able to find anything that would explain this being worse with Crucible I can confirm that I never suffered this problem prior to Crucible. Could it be something related to changing the session timers?
We know that the problem got more noticeable with the first step of enabling Time Dilation, which was in the middle of December, but the main change was several months earlier. With Crucible 1.1 the behavior was improved - but apparently not enough for users with a high clock drift. Crucible 1.2 should have not changed the behavior in any way - as far as we can tell.
CCP Habakuk | EVE Quality Assurance
|
|
|
CCP Habakuk
C C P
C C P Alliance
186
|
Posted - 2012.03.02 17:26:00 -
[10] - Quote
Hey, just a short update: We were able to gather some useful data regarding this in yesterday's mass-test on Singularity, which is now being analyzed.
CCP Habakuk | EVE Quality Assurance
|
|
|
|
|
CCP Habakuk
C C P
C C P Alliance
186
|
Posted - 2012.03.07 15:24:00 -
[11] - Quote
Molic Blackbird wrote:Will the Crucible 1.5 patch contain solutions that help alleviate this problem?
Yes, Crucible 1.5 will contain improvements to this problem. We don't know yet if they are sufficient, but we hope, that these will hide the problem as much, that you won't notice it while playing. We are still investigating possible software causes for this problem which might lead to better solutions after Crucible 1.5
[shameless plug] These improvements will be active in tomorrow's mass test on Singularity. Feel free to join the mass test, if you experience this problem on TQ and want to check it out. If you manage to gather logs and send these through a bugreport: Even better! [/shameless plug]
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
188
|
Posted - 2012.03.12 20:24:00 -
[12] - Quote
This is indeed missing in the patch notes, as the real fix is still not made - but the values of the existing clock-sync are being changed, so that a basic check is done every 5 minutes (and more often if clock drift problems are detected) and we are now allowing to correct more than 2% of clock drift.
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
189
|
Posted - 2012.03.14 11:51:00 -
[13] - Quote
azrael211 wrote:Greatly improved...thank you. When running 2 clients there is still a delay of around 10-30 secs in some jumps but at least I can now play with 2 accounts at once.
Good to hear this! I would be very interested in a log from one of these 10-30 sec delays. If you manage to get logs please attach them to a bugreport and include my name in the title of the bugreport.
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
190
|
Posted - 2012.03.15 12:24:00 -
[14] - Quote
azrael211 wrote:CCP Habakuk wrote:azrael211 wrote:Greatly improved...thank you. When running 2 clients there is still a delay of around 10-30 secs in some jumps but at least I can now play with 2 accounts at once. Good to hear this! I would be very interested in a log from one of these 10-30 sec delays. If you manage to get logs please attach them to a bugreport and include my name in the title of the bugreport. Sure, does it make a difference how i run the logging app with 2 clients running?
Just start the app before starting the clients - it will log both client, which is good (we can then compare the logs of both clients and it is easy to filter for one of those if we want to).
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
191
|
Posted - 2012.03.28 18:33:00 -
[15] - Quote
Hey! Sorry for resurrecting this thread: We have a potential fix for this problem ready and will be testing it in a mass test tomorrow.
More info can be found in this forum thread.
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
191
|
Posted - 2012.03.29 00:56:00 -
[16] - Quote
Zekyll wrote:After reading this thread it's not quite clear to me whether CCP is even trying to look for possible causes to the clock drift. All the replies seem to be assuming that it's a hardware problem and nothing can be done about it, just mitigate the symptoms by syncing with server time
I just had to bring this up because I've had some HUGE clock drift since Crucible 1.5, and it only seems to occur when running EVE. Just starting the client and staying in the login screen makes my system clock lose consistently 5 seconds every minute. I have not been able to reproduce it with any other program or game, and outside EVE the clock runs just fine. I've also noticed that the drift is proportional to frame rate. For example if I run with interval four (15fps) I only lose about 1 second per minute
Maybe it is a problem with hardware, drivers or something, but at the very least it tells me that EVE client has to be doing some really weird stuff that no other program does to reveal the problem
Gonna make a bug report too; just wanted to post here for everyone to see
Win XP Pro SP3 32bit / Intel Q9450 / 4GB / Abit IP35 / 8800 GTS 51
We have indeed found an EVE-specific issue, which causes this clock-drift, but apparently only on some hardware. I experienced this problem on my work PC quite heavily during a mass-test on the 1st of March (while running 2 clients at high settings, one of them with enhanced logging).
CCP Veritas analyzed these (and other) logs and found a very low-level problem in the EVE client with smoothing the time in some circumstances (probably related to hardware, drivers and high CPU load), which caused the clock to drift. This problem was probably around for years, but is only visible since Time Dilation enforced the proper time at jumping between nodes.
The fixes in Crucible 1.2 and Crucible 1.5 treated the symptoms by trying to compensate the clock drift. The fix in tomorrow's mass-test is trying to solve the root issue of the insufficient / wrong smoothing of time. Internal tests are very promising - but this is no proof yet, that it really works on all hardware.
I hope this explains the issue a bit - more technical details will need to come from CCP Veritas.
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
CCP Habakuk
C C P
C C P Alliance
192
|
Posted - 2012.04.02 11:18:00 -
[17] - Quote
I have good and bad news regarding this problem:
The bad news: I was able to verify, that my clock drifted a bit in some test cases (straining the computer with extreme graphic settings at 100% CPU) even after the latest improvement. In these cases the computer clock itself drifted (together with the EVE client clock). The cases of the EVE client clock drifting away from the computer clock should be fixed on the other hand.
The good news: The fix for the EVE client clock drifting is scheduled for being released tomorrow.
CCP Habakuk | EVE Quality Assurance | Team Gridlock
Writing bug reports | Mass tests
|
|
|
|
| |
|